There are 100% strict requirements of how evolved Java code strings are represented,
including that all newlines are "\n", the code contains no "\r", UTF-8,
no trimming strings, and string length is 100% predictable after many changes.

If your text editor can not handle "\n" and UTF-8, find a better one.

Any time Audivolv finds "\r" in evolved Java code,
it should be removed this way: code = code.replace("\r\n","\n").replace("\r","\n"); 

Why is Audivolv so strict about evolved strings of Java code?
There is only 1 way to interpret "the var name at char index (base-ten)1509 in a code string".
Complete predictability (in lower-level areas) results in less bugs and more progress.
This only applies to Java code in memory. You can save/load it however you want in files.
